projects / gtk4.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 0dcb9b3) | patch
gdk: Address pad events similarly to keyboard events
authorCarlos Garnacho <carlosg@gnome.org>
Thu, 4 Aug 2016 17:10:21 +0000 (19:10 +0200)
committerCarlos Garnacho <carlosg@gnome.org>
Tue, 23 Aug 2016 19:01:44 +0000 (21:01 +0200)
commitf1a9cd466e48243ff6a3592b933bab2336e8c04d
tree6518189bd42bbfb019025dd5986e0876af9093bftree | snapshot
parent0dcb9b316e704071e98d67668c99a20e3a9cd425commit | diff
gdk: Address pad events similarly to keyboard events

We want the same treatment for those, the event will be emitted on the
toplevel, which will then decide what to do with the event.

It just doesn't make much sense to propagate those up/down the hierarchy,
when we want specifically one action being triggered from those.

https://bugzilla.gnome.org/show_bug.cgi?id=770026
gdk/gdkwindow.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.